Method and system for vehicle inspection

ABSTRACT

A system and method for using a mobile device to capture the proper execution of a series of one or more tasks with pre-assigned constraints that are associated with a specific set of assets is disclosed herein. The assets have certain known physical attributes and characteristics and are configured in a known manner. The assets are preferably vehicles such as trucks.

CROSS REFERENCES TO RELATED APPLICATIONS

The Present Application claims priority to U.S. Provisional Patent Application No. 63/020,001, filed on May 4, 2020, and the Present Application is also a continuation-in-part application of U.S. patent application Ser. No. 16/927,231, filed on Jul. 13, 2020, which claims priority to U.S. Provisional Patent Application No. 62/873,922, filed on Jul. 14, 2019, and U.S. patent application Ser. No. 16/927,231 is a continuation-in-part application of U.S. patent application Ser. No. 16/870,955, filed on May 9, 2020, which is a continuation-in-part application of U.S. patent application Ser. No. 16/416,396, filed on May 20, 2019, now U.S. patent Ser. No. 10/652,935, issued on May 12, 2020, which is a continuation-in-part application of U.S. patent application Ser. No. 16/118,436, filed on Aug. 31, 2018, now U.S. patent Ser. No. 10/334,638, issued on Jun. 25, 2019, which is a continuation application of U.S. patent application Ser. No. 15/917,633, filed on Mar. 11, 2018, now U.S. patent Ser. No. 10/070,471, issued on Sep. 4, 2018, which is a continuation application of U.S. patent application Ser. No. 15/624,814, filed on Jun. 16, 2017, now U.S. Pat. No. 9,961,710, issued on May 1, 2018, which claims priority to U.S. Provisional Patent Application No. 62/352,014, filed on Jun. 19, 2016, and U.S. patent application Ser. No. 16/927,231 is a continuation-in-part application of U.S. patent application Ser. No. 16/664,906, filed on Oct. 27, 2019, now U.S. patent Ser. No. 10/803,682, issued on Oct. 13, 2020, which is a continuation application of U.S. patent application Ser. No. 15/859,380, filed on Dec. 30, 2017, now U.S. patent Ser. No. 10/475,258, issued on Nov. 12, 2019, which is a continuation-in-part application of U.S. patent application Ser. No. 15/624,814, filed Jun. 16, 2017, now U.S. Pat. No. 9,961,710, issued on May 1, 2018, which claims priority to U.S. Provisional Patent Application No. 62/352,014, filed on Jun. 19, 2016, and U.S. patent application Ser. No. 15/859,380 claims priority to U.S. Provisional Patent Application No. 62/441,290, filed on Dec. 31, 2016, U.S. Provisional Patent Application No. 62/441,298, filed on Dec. 31, 2016, and U.S. Provisional Patent Application No. 62/441,315, filed on Dec. 31, 2016, each of which is hereby incorporated by reference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT Not Applicable BACKGROUND OF THE INVENTION Field of the Invention

The present invention generally relates to inspecting vehicles.

Description of the Related Art

The prior art discusses various techniques for inspecting vehicles.

General definitions for terms utilized in the pertinent art are set forth below.

Beacon is a management frame that contains all of the information about a network. In a WLAN, Beacon frames are periodically transmitted to announce the presence of the network.

BLUETOOTH technology is a standard short range radio link that operates in the unlicensed 2.4 gigaHertz band.

Code Division Multiple Access (“CDMA”) is a spread spectrum communication system used in second generation and third generation cellular networks, and is described in U.S. Pat. No. 4,901,307.

Electronic logging devices (ELD) and electronic on-board recorders (EOBR) are devices used on commercial motor vehicles to determine a position of the vehicle.

FTP or File Transfer Protocol is a protocol for moving files over the Internet from one computer to another.

GSM, Global System for Mobile Communications is a second generation digital cellular network.

Hypertext Transfer Protocol (“HTTP”) is a set of conventions for controlling the transfer of information via the Internet from a web server computer to a client computer, and also from a client computer to a web server, and Hypertext Transfer Protocol Secure (“HTTPS”) is a communications protocol for secure communication via a network from a web server computer to a client computer, and also from a client computer to a web server by at a minimum verifying the authenticity of a web site.

Internet is the worldwide, decentralized totality of server computers and data-transmission paths which can supply information to a connected and browser-equipped client computer, and can receive and forward information entered from the client computer.

Media Access Control (MAC) Address is a unique identifier assigned to the network interface by the manufacturer.

Memory generally includes any type of integrated circuit or storage device configured for storing digital data including without limitation ROM, PROM, EEPROM, DRAM, SDRAM, SRAM, flash memory, and the like.

Organizationally Unique Identifier (OUI) is a 24-bit number that uniquely identifies a vendor, manufacturer, or organization on a worldwide basis. The OUI is used to help distinguish both physical devices and software, such as a network protocol, that belong to one entity from those that belong to another.

Probe Request: A frame that contains the advertisement IE for a device that is seeking to establish a connection with a proximate device.

Probe Response: A frame that contains the advertisement IE for a device. The Probe Response is sent in response to a Probe Request.

Processor generally includes all types of processors including without limitation microprocessors, general purpose processors, gate arrays, array processors, application specific integrated circuits (ASICs) and digital signal processors.

SSID (Service Set Identifier) is a 1 to 32 byte string that uniquely names a wireless local area network.

Transfer Control Protocol/Internet Protocol (“TCP/IP”) is a protocol for moving files over the Internet.

URL or Uniform Resource Locator is an address on the World Wide Web.

User Interface or UI is the junction between a user and a computer program. An interface is a set of commands or menus through which a user communicates with a program. A command driven interface is one in which the user enter commands. A menu-driven interface is one in which the user selects command choices from various menus displayed on the screen.

Web-Browser is a complex software program, resident in a client computer, that is capable of loading and displaying text and images and exhibiting behaviors as encoded in HTML (HyperText Markup Language) from the Internet, and also from the client computer's memory. Major browsers include MICROSOFT INTERNET EXPLORER, NETSCAPE, APPLE SAFARI, MOZILLA FIREFOX, and OPERA.

Web-Server is a computer able to simultaneously manage many Internet information-exchange processes at the same time. Normally, server computers are more powerful than client computers, and are administratively and/or geographically centralized. An interactive-form information-collection process generally is controlled from a server computer, to which the sponsor of the process has access.

Wireless Application Protocol (“WAP”) is an open, global specification that empowers users with mobile wireless communication devices (such as mobile phones) to easily access data and to interact with Websites over the Internet through such mobile wireless communication device. WAP works with most wireless communication networks such as CDPD, CDMA, GSM, PDC, PHS, TDMA, FLEX, reflex, iDEN, TETRA, DECT, DataTAC, Mobitex and GRPS. WAP can be built on most operating systems including PalmOS, WINDOWS, CE, FLEXOS, OS/9, JavaOS and others.

WAP Push is defined as an encoded WAP content message delivered (pushed) to a mobile communication device which includes a link to a WAP address.

Wireless AP (access point) is a node on the wireless local area network (WLAN) that allows wireless devices to connect to a wired network using Wi-Fi, or related standards.

There is a need for a better system for inspecting a vehicle such as a truck.

BRIEF SUMMARY OF THE INVENTION

The present invention provides a system and method for using a mobile device to capture the proper execution of a series of one or more tasks with pre-assigned constraints that are associated with a specific set of assets, where those assets have certain known physical attributes and characteristics and are configured in a known manner.

One aspect of the present invention is a system for capturing the proper execution of a series of one or more tasks with pre-assigned constraints that are associated with one or more assets, wherein the assets comprise a plurality of certain physical attributes and characteristics in a known configuration. The system comprises a mobile device comprising: wireless connectivity, with Radio Frequency capabilities that include one of more of WiFi, Bluetooth, 3G/LTE/5G, GPS or their variations and/or evolutions; onboard processing; storage; touch or voice to text input; Sensors that may include one or more of movement, thermal, pressure, moisture, or vibration sensing capabilities; and positional detecting equipment to include one or more of gyroscopes, an accelerometer, a magnetometer or other compass heading sources capable of computing positioning in 3 axis, changes to position in 3 axis, distance and path taken as changes are being computed.

Another aspect of the present invention is a method of using a mobile device to capture the execution of a series of one or more tasks with pre-assigned constraints that are associated with a specific set of assets, where those assets have certain known physical attributes and characteristics in a known configuration.

Yet another aspect of the present invention a non-transitory computer-readable medium that stores a program that causes a processor to perform functions for using a mobile device to capture the execution of a series of one or more tasks with pre-assigned constraints that are associated with a specific set of assets, where those assets have certain known physical attributes and characteristics in a known configuration.

Yet another aspect of the present invention is a method for performing an electronic driver verification inspection report for an asset.

Yet another aspect of the present invention is a system for capturing the proper execution of a series of one or more tasks with pre-assigned constraints that are associated with at least one asset. The system comprises at least one asset and a mobile device. The at least one asset comprises a plurality of physical attributes and characteristics in a known configuration. The mobile device comprises a wireless transceiver, a processor for onboard processing, a memory, at least one user interface, a plurality of sensors, and a plurality of positional detecting components. The mobile device is configured to capture the execution of a series of one or more tasks with pre-assigned constraints that are associated with the at least one asset.

Yet another aspect of the present invention is a system for an electronic driver verification inspection report for an asset. The system comprises a mobile device and an asset. The mobile device comprises a processor, a graphical user interface, a memory, a plurality of sensors, a wireless transceiver and a mobile application. The asset comprises a plurality of set inspection points, each of the plurality of set inspection points at a known position on the asset and physically positioned from any other of the plurality of set inspection points. The mobile application is configured to utilize at least one of the plurality of sensors to verify an inspection of an inspection point of the plurality of set inspection points when the mobile device is within a pre-determined distance from the inspection point.

Yet another aspect of the present invention is a method for performing an electronic driver vehicle inspection report for an asset. The method includes receiving an assignment at an AMCD that is associated with an operator selected by the assigning authority to complete the assignment. The method also includes initializing the assignment on the AMCD. The method also includes capturing and storing changes from an initial position at the asset. The method also includes performing the inspection of the asset using the AMCD. The method also includes completing the inspection.

Having briefly described the present invention, the above and further objects, features and advantages thereof will be recognized by those skilled in the pertinent art from the following detailed description of the invention when taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a block diagram of a system for inspection of a vehicle.

FIG. 1A is a block diagram of a system for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources.

FIG. 2 is a block diagram of a system for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources.

FIG. 3 is a block diagram of a system for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources.

FIG. 4 is an illustration of multiple sensors on a truck.

FIG. 4A is an illustration of multiple sensors on a truck connected to a BUS for the truck.

FIG. 5 is an isolated view of an operator using a mobile device for a vehicle inspection.

FIG. 6 is a top plan view of an inspection of a vehicle.

FIG. 7 is a top plan view of an inspection of a vehicle.

FIG. 8 is a top plan view of an inspection of a vehicle.

FIG. 9 is a flow chart for a method for performing an electronic driver vehicle inspection report for an asset.

FIG. 10 is a flow chart for a method for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources.

FIG. 11 is a block diagram of system for a secure communication protocol for connecting a wireless device to a single access point in a vehicle.

FIG. 11A is a continuation of the block diagram of FIG. 1 .

FIG. 12 is a flow chart of a method for a secure connection to a wireless network of a vehicle.

FIG. 13 is an illustration of a driver identifying a vehicle through connection of a tablet computer to an unpublished network.

FIG. 14 is an isolated view of general electrical components of a mobile communication device.

FIG. 15 is an isolated view of general electrical components of a server.

FIG. 16 is a flow chart of method for securely connecting a wireless device to a single access point in a vehicle.

FIG. 17 is an illustration of a driver identifying a vehicle through connection of a tablet computer to an unpublished network.

DETAILED DESCRIPTION OF THE INVENTION

A preferred embodiment is a system for an electronic driver verification inspection report for a vehicle. The system comprises a mobile device and a vehicle. The mobile device comprises a processor, a graphical user interface, a memory, sensors, a wireless transceiver and a mobile application. The vehicle comprises a set of inspection points, with each of the inspection points at a known position on the vehicle and physically positioned from any other of the inspection points. The mobile application is configured to utilize at least one of the sensors to verify an inspection of an inspection point when the mobile device is within a pre-determined distance from the inspection point.

The following definitions are used herein:

“Assignment”: One or more tasks, that in total are the GROUP OF TASKS and the TASK ASSETS.

“Group of Tasks” consist of one or more discrete jobs which require operator input and are bound by a set of constraints that include but are not limited to time, location and specific action completions.

“Task Assets” are one or more physical assets with certain physical attributes known to the Assignment, that are configured in a manner that is known to the Assignment, and whose configuration and known physical attributes associated with the temporal configuration existing during the time the Group of Tasks are being executed, can be used to calculate constraints to the execution of the group of tasks.

“Approved Mobile Computing Device”: An Approved Mobile Computing Device (AMCD) is a device that contains: (a) wireless connectivity, with Radio Frequency capabilities that include one of more of WiFi, Bluetooth, 3G/LTE/5G, GPS or their variations and/or evolutions; (b) onboard processing; (c) storage; (d) optional human interfaces to include touch or voice to text input; (e) Sensors that may include one or more of movement, thermal, pressure, moisture, or vibration sensing capabilities; and (f) positional detecting equipment to include one or more of gyroscopes, an accelerometer, a magnetometer or other compass heading sources capable of computing positioning in 3 axis, changes to position in 3 axis, distance and path taken as changes are being computed.

“Validated Source”: A validated source includes but is not limited to a capability to: validate in real time that the Task Assets being evaluated are geographically co-located with the AMCD within Assigning Authority configured proximity definitions; contemporaneously validate during the period of Assignment completion specific information such as the vehicle identification number, serial number, or other discrete high-confidence identifying information that confirms that the assets being evaluated are the appropriate discrete assets identified in the Assignment, and no others.

“Initial Position”: Initial Position (IPOS) is the position described when an Operator selects “Initialize” and is generated by polling and combining information provided by one or more available onboard sensors and/or sources to include a. GPS, b. Accelerometer, c. Magnetometer and/or other sources of Cardinal Heading information, d. Radio Frequency position as determined by Decibel and Radial from a known fixed emitting source.

“Position Engine”: Utilizing the capabilities of the AMCD and capturing Sequence Positions.

“Initial Execution Constraints”: Those items that must be satisfied before the Operator can begin satisfying the Assigning Authority assigned tasks. Conditions are configurable by the Assigning Authority, but may include conditions such as Vehicle or Task Asset(s) position or state, Driver status, AMCD state, and Assignment Initialization status.

Sequence Position: The position of the asset at each sequence.

Terminal Position: The position of the asset at the end of the assignment.

Preparation for Operation

A temporal assignment is generated by an assigning authority and the assignment is composed of:

One or more Task Assets, which have accessible “asset profiles” that include descriptions of one or more of the following: a. physical characteristics b. points of interest, c. instructions, and/or d. additional information.

One or more Task Asset configurations, where more than one Asset is included in the Assignment, and there are known and/or expected combinations of those Assets that yield combined geometries or other characteristics relevant to the boundary conditions associated with task completion.

One or more “Tasks,” where tasks are described as sets of activities that an operator must complete based on a set of know constraints and measurable actions.

Assignment is delivered to an AMCD that is associated with an Operator selected by the Assigning Authority to complete the Assignment.

Assignment becomes executable when the Assignment's INITIAL EXECUTION CONSTRAINTS are satisfied.

Operational Function and Execution

“START”: Operator INITIALIZES AMCD by selecting operator accessible INITIALIZE command. When initializing is complete, START button becomes functional.

Operator selects START command through positive confirmation and begins ASSIGNMENT.

As Operator changes the location, position and orientation of the AMCD, the AMCD begins capturing and storing changes from INITIAL POSITION to include: Accelerometer state, and one or more of the following: Magnetometer and/or other Compass heading source data current position information; Decibel and bearing information from a known Radio Frequency Source (“RF Source”).

At configurable intervals, these changes are combined to create discrete SEQUENCE POSITIONS which describe a series of positions using data generated by 1, 1.1, 1.2 at any discrete point in time, with a naming convention that allows these positions to be reassembled at any time subsequent to their capture (e.g., an ascending alphanumeric naming convention), in an order that replicates the geospatial position of the AMCD at the time of the capture of each Sequence Position.

When an accelerometer indicates a change from an Initial Position Accelerometer State, the device begins storing accelerometer data and changes based on configurable user specified increments. The changes from that position are calculated using:

MOVE

MEASURE

CAPTURE

REPEAT

COMPLETE

a. sequential changes in Magnetometer or other Compass heading source;

b. changes in signal strength and bearing from a known RF source.

Assignment—Combine Tasks with elements from DBs, create temporal bounds, constraints, rules.

Tasks

Task DB

Configurable Tasks

Databases

Asset DB

Vehicle

Trailer

Accessory

Asset Configuration—Combination of assets selected from Database, and known geometric combination(s) of those assets.

Is Asset Inspection Configuration “DEFAULT” ?

Yes/No

If “Yes”

Pathway Defined

Envelope Defined

Sequence Defined

Operator Initiates Assignment

Position Engine real time processing

Position Engine feeds Task engine (where applicable and default)

Task initiation executed by driver, or prompted by AMCD when default is validated

Task execution compared to task requirement list and validated/in-validated in real time if default, or subset of defaults. If no default conditions available, info stored

Task completion defined when tasks are exhausted, and/or Operator indicates Assignment complete

Completed task list path and execution performance compared to Assignment requirements for validation.

If complete, Operator receives “Completion” confirmation

If not complete, incomplete tasks are identified and remedial actions described

Operator completes remedial actions until Assigning Authority conditions satisfied

When Satisfies “Complete” confirmation made available to Operator.

If “No”

Pathway=“Null”

Envelope=“Null”

Sequence Defined

Operator Initiates Assignment

Position Engine real-time processing of Operator activity

Position Engine feeds Task engine (where applicable and default)=“null”

Task initiation executed by driver, or prompted by AMCD when default is validated=“null”

Driver Initiates Task through AFFIRMATIVE ACTION

Task execution compared to task requirement list and validated/in-validated in real time if default, or subset of defaults. If no default conditions available, info stored (validates which ever values can be satisfied without knowing the path)

Initial Task Completion defined when a. tasks are exhausted, and/or b. Operator indicates Assignment complete through positive confirmation action

Completed task list path and execution performance compared to Assignment requirements for validation.

Completed path list is compared to configuration library and “best fit” to account for changes in geometry from DEFAULT GEOMETRY

If “BEST FIT PATH” satisfies conditions for tasks, those tasks are validated

If “BEST FIT PATH” does not satisfy task conditions, those tasks are identified with remedial actions indicated

Operator executes remedial actions until all actions are complete, or driver “opts out” of task where applicable as defined by Assigning Authority

Final completion and “Opt Out” report completed

If complete, Operator receives “Final Completion” confirmation

If not complete, incomplete tasks are identified and remedial actions described

Operator completes remedial actions until Assigning Authority conditions satisfied

When Satisfies “Complete” confirmation made available to Operator.

In one embodiment, a system comprises an assigning authority engine, a remote profile manager toolset, databases, cloud sources, a vehicle and a CVD within the vehicle. The contents of each of the databases are accessible and combinable by the assigning authority to produce dynamic, temporal combinations of data elements and instructions for the vehicle. The assigning authority is configured to use the remote profile manager toolset to execute the dynamic, temporal combinations. The dynamic, temporal combinations access data from the cloud sources comprising third party data and vehicle, timing, event, and/or positioning (“VTEP”) data to inform instruction sets delivered by the assigning authority. One or more elements of the VTEP data is used as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. A single coherent information picture is form from fusing data and computational information from on-vehicle and off-vehicle sources.

The cloud source comprises a telematics service provider cloud, an original equipment cloud (truck manufacturer, Tier 1 supplier, device supplier and the like), a customer cloud (end user) and a public cloud.

The system also includes infrastructure comprising at least one of a building, a gate, an access controlled point of entry, a parking structure, a weigh station, a toll collection structure, a fueling equipment and a vehicle service equipment.

Multiple vehicle connected mobility devices are used with the system 1600 and comprise at least one of a tablet computer, a mobile phone, a scanning device, a beacon, a RF passive or active communication device and a signature capture device.

Affiliates with the system include at least one of another vehicle authorized to share data via V2V, Cloud, or other RF communication protocols, a TMS system authorized by the assigning authority to directly take data from or provide data to the vehicle CVD, an authorized cloud provider, and an authorized user granted access by the assigning authority.

The vehicle is preferably one of a long-haul semi-truck, a bus, a sedan, a pick-up, a sports utility vehicle, a limousine, a sports car, a delivery truck, a van, or a mini-van.

The vehicle has multiple endpoints with direct connectivity to the CVD/vehicle, and require no routing through the Cloud. The endpoints are user interfaces or built in displays, devices connected through fixed or wireless connection to the vehicle's CVD, sensors connected through the vehicle bus to the CVD, or directly to the CVD via wired or wireless connection, like devices. The vehicle is a primary generator and source of VTEP data.

The RPM comprises a RPM sync for syncing with other devices, servers, Cloud, the CVD and the like.

A system 100 for an inspection of a vehicle is shown in FIG. 1 . The vehicle is preferably a truck, however, those skilled in the pertinent art will recognize that the truck may be replaced by any type of vehicle (such as a bus, sedan, pick-up, sport utility vehicle, limousine, sports car, delivery truck, van, mini-van, motorcycle, and the like) without departing from the scope of spirit of the present invention. The truck preferably comprises a motorized engine, a vehicle identification number (“VIN”), an on-board computer with a memory and a connector plug. The on-board computer preferably has a digital copy of the VIN in the memory. The on-board computer is preferably in communication with the motorized engine. The truck may also have a GPS component for location and navigation purposes, a satellite radio such as SIRIUS satellite radio, a driver graphical interface display, a battery, a source of fuel and other components found in a conventional long distance truck.

Also in the truck is a CVD 135 comprising a processor, a WiFi radio, a BLUETOOTH radio, a memory and a connector to connect to the connector plug of the on-board computer.

A driver 205 preferably has a mobile communication device such as a tablet computer 110 in order to pair with a wireless network generated by the CVD 130 of the truck. The tablet computer 110 preferably comprises a graphical user interface 335, a processor 310, a WiFi radio 307, a BLUETOOTH radio 306, and a cellular network interface 308.

FIG. 1A is a block diagram of a system 1100 for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. The system 1100 includes a vehicle 1000, an assigning authority engine 1105, a remote profile manager (RPM) toolset 1130 with an RPM sync program 1135, and a plurality of databases 1125, both accessible through the cloud 1110. A vehicle 1000 preferably includes a CVD 135. The remote profile manager toolset 1130 preferably includes a server 1135. The plurality of databases 1125 is preferably composed of multiple databases 1125 a-d.

The assigning authority engine 1105 preferably has a work assignment that has been generated for a specific vehicle 1000. In a preferred embodiment, the assigning authority engine 1105 resides at a server for the system 1100, and the RPM toolset 1130 resides at a separate server. Alternatively, the assigning authority engine 1105 and the RPM toolset 1130 reside at the same server. The assigning authority engine 1105 is preferably configured to access and combine off-vehicle content and on-vehicle data, along with the work assignment, to produce dynamic, temporal combinations of data elements and instructions for the vehicle 1000. Additionally, the assigning authority engine 1105 provides permission to various applications to share data for app-to-app integration. In one example, the assigning authority engine 1105 grants permission to a workflow application running on a mobile communication device for the vehicle 1000 to obtain data from a navigation application running on the mobile communication device. The assigning authority engine 1105 instructs the navigation application to hare the data with the workflow application. In one specific example, the share data is GPS coordinates for the vehicle.

FIG. 2 is a block diagram of a system 1500 for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. At step A, VTEP data is gathered from multiple databases, cloud services and other off-vehicle sources, as well as on-vehicle sources. At step B, the RPM toolset is used to configure multiple assigning authority rules based on the collected VTEP data. At step C, multiple instruction sets are delivered to multiple cloud services, other off-vehicle sources and on-vehicle sources. At step D, off-vehicle sources such as physical infrastructure, vehicles, mobile devices, and mobile device applications share data per the delivered instruction sets. At step E, back office managers, physical infrastructure, on-vehicle and off-vehicle sources are provided with new information data set combinations enabling novel processing capabilities for the system.

In one embodiment, the off-vehicle source is a mobile application operating on a mobile device, and the data originates from the mobile application.

In another embodiment, app to app integration is utilized to generate the information data set. The app to app integration is performed at a remote server, within an app on a mobile device, on a CVD or a combination thereof.

The cloud sources preferably comprise a public cloud source, a private cloud source, a hybrid cloud source, a multi-cloud source, a service provider cloud, a telematics service provider cloud, an original equipment manufacturer cloud (truck manufacturer, Tier 1 supplier, device supplier and the like), a customer cloud (end user) and/or a public cloud.

The system also preferably includes physical infrastructures with communication devices comprising at least one of a building, a gate, an access controlled point of entry, a parking structure, a weigh station, a toll collection structure, a fueling equipment and a vehicle service equipment. In one embodiment, a passive device on a physical structure broadcasts a unique ID which is received by a mobile device and a vehicle gateway device. If the passive device is a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement.

Multiple vehicle connected mobility devices are preferably used with the system 1600 and comprise at least one of a tablet computer, a mobile phone, a scanning device, a beacon, a RF passive or active communication device and a signature capture device.

Affiliates with the system 1600 include at least one of another vehicle authorized to share data via vehicle-to-vehicle (V2V), Cloud, or other RF communication protocols, a TMS system authorized by the assigning authority engine 1105 to directly take data from or provide data to the vehicle CVD 135, an authorized cloud provider, and an authorized user granted access by the assigning authority.

The vehicle 1000 is preferably one of a long-haul semi-truck, a bus, a sedan, a pick-up, a sports utility vehicle, a limousine, a sports car, a delivery truck, a van, or a mini-van.

FIG. 3 is a block diagram of a system 1300 for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. As shown in FIG. 3 , the system 1300 comprises an assigning authority engine 1105, a remote profile manager toolset 1130, databases (FIG. 2 ), cloud sources, a vehicle 1000 and a CVD 135 within the vehicle 1000. The cloud sources include main protected server/cloud 1183, an original equipment manufacturer server/cloud 1182, a customer server/cloud 1181 and a public server/cloud 1180. Multiple other servers/clouds and/or databases can be utilized with the present invention without departing from the scope and spirit of the claims. The cloud sources, databases, RPM 1130 and assigning authority engine 1105 communicate with the CVD 135 utilizing various wireless communication protocols including WiFi, cellular networks, BLUETOOTH, GPS, and the like. The contents of each of the databases (2001-2008) and cloud sources are accessible and combinable by the assigning authority engine 1105 to produce dynamic, temporal combinations of data elements and instructions for the vehicle 1000. The assigning authority engine 1105 is configured to use the remote profile manager toolset 1130 to execute the dynamic, temporal combinations. The dynamic, temporal combinations access data from the cloud sources comprising third party data and vehicle, timing, event, and/or positioning (“VTEP”) data 1160 to inform instruction sets delivered by the assigning authority engine 1105. The instruction sets are preferably temporal permission for the on-vehicle sources and off-vehicle sources (e.g., applications) to connect and share data with each other. One or more elements of the VTEP data 1160 is used as the basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. A single coherent information picture 1170 is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources. The new information data set combination (single coherent information picture) is a display of information generated from the combination of data from the on-vehicle sources and the off-vehicle sources. The data set can include dynamic route information (road condition changes due to weather, construction and the like), an updated driver's profile, vehicle engine date, cargo data, dynamic compliance rules, micro-navigation data, fuel stop data, inspection stations on the route, wireless communications connectivity status, time to destination, and the like. An example of a new information data set combination is imparting GPS location data from a truck/CVD onto cargo (the potato chips example). The new information data set combination is preferably any new combination of the connected data sources data for the specific vehicle of interest.

As shown in FIG. 3 , the vehicle 1000 has multiple endpoints with direct connectivity to the CVD 135, and requires no routing through a cloud service. The endpoints are user interfaces or built in displays, devices connected through fixed or wireless connection to the vehicle's CVD 135, sensors connected through a vehicle bus (see FIG. 4A) to the CVD 135, or directly to the CVD 135 via wired or wireless connection, like devices. The vehicle 1000 is preferably a primary generator and source of VTEP data 1160.

The RPM 1130 preferably comprises a RPM sync 1135 for syncing with other devices, servers, the Cloud, the CVD and the like.

The real-time data for the vehicle 1000 preferably comprises a real-time speed of the vehicle, tire pressure values from a plurality of tire sensors, refrigeration/HVAC unit values, a plurality of fluid levels, a plurality of power unit values, a real-time fuel tank capacity, and a fuel type.

The plurality of configurable real-time vehicle data trigger events comprises a value outside of a predetermined range for the real-time data of the vehicle.

The real-time driver/operator profile comprises amount of time driving during a pre-determined time period, number of rest breaks during the pre-determined time period, license compliance data, physical disabilities and driving violations.

One example of an off-vehicle source is a fuel stop. A profile of a fuel stop preferably comprises real-time types of fuels available, set billing instructions, physical dimensions of a plurality of fuel pumps, GPS coordinates, hours of operation, food service availability, and resting area availability. The predetermined fueling time period is a time range to fuel the vehicle based on the real-time GPS location of the vehicle, the real-time speed of the vehicle, the distance to the selected fuel stop from the real-time GPS location of the vehicle, and the hours of operation of the fuel stop.

A configuration of the vehicle 1000 is preferably selected from one of a single trailer, a dual trailer, a triple trailer, and a refrigeration trailer.

Another example of an off-vehicle source is a database (Federal, State local) with dynamic compliance rules. The dynamic compliance rules comprise speed limits, transport of toxic waste, the transport of refrigerated cargo, the rest durations for drivers/operators, the necessary insurance coverage, and the type of taxes and fees to be paid.

The workflow utilized by the assigning authority engine 1105 preferably comprises an origination location of the vehicle, a destination of the vehicle, a route to the destination, a cargo, a time of departure and a time of arrival.

In one non-limiting example, the assigning authority engine 1105 receives data over the cloud from a customer server 1181 that a shipment of bags of potato chips were damaged in transit. The assigning authority engine 1105 accesses a CVD 135 or mobile device for the vehicle that delivered the bags of potato chips to determine the origination location, the destination location and the route. The assigning authority engine 1105 uses a navigation app on the mobile device (tablet computer) to determine the route, and an elevation of the route. The assigning authority engine 1105 determines that the vehicle traveled over a high elevation mountain range that probably resulted in the damage to the bags of potato chips due to a pressure differential. The assigning authority engine 1105 uses this information to reroute a subsequent shipment of bags of potato chips to avoid the high elevation mountain range.

FIG. 4 is an illustration of multiple sensors on a truck 1000. The vehicle/truck 1000 preferably comprises an oil level sensor 1005, an engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020, a temperature sensor 1025, a tire pressure sensor 1030, and a fuel sensor 1035. Those skilled in the pertinent art will recognize that multiple other sensors may be utilized without departing from the scope and spirit of the present invention. FIG. 4A is an illustration of multiple sensors on a truck connected to a data bus for the truck. Each of the sensors (oil level sensor 1005, engine sensor 1010, a power sensor 1015, a refrigeration/HVAC sensor 1020, a temperature sensor 1025, tire pressure sensors 1030 a-d, and fuel sensor 1035) is preferably connected to the data bus for transferring data to an on-board computer of the vehicle 1000, or directly to the CVD 135. Alternatively, some or all of the sensors use wireless communications to communication with the CVD 135.

FIG. 5 is an isolated view 515 of an operator using a mobile device 110 for a vehicle inspection. The mobile device 110 preferably comprises a processor 53, a memory 54, a thermistor 56, a speaker 55, an accelerometer 57, and wireless transceivers 52.

FIG. 6 is a top plan view of an inspection of a vehicle 210. The vehicle comprises a set inspection points (A-J), with each of the inspection points at a known position on the vehicle and physically positioned from any other of the inspection points (A-J). The mobile application is configured to utilize at least one of the sensors to verify an inspection of an inspection point when the mobile device is within a pre-determined distance from the inspection point. The vehicle 210 has multiple sensors 80-89 that are located at important components of the vehicle 210 in relation to a set assignment for the vehicle. An operator accesses a mobile device and begins an inspection at an inspection point A to receive a sensor signal from sensor 80. The operator continues the inspection around the vehicle at points B-J, receiving signals from sensors 81-89.

FIG. 7 is a top plan view of an inspection of a vehicle. The vehicle has multiple sensors 71-80 that are located at important components of the vehicle 210 in relation to an assignment.

FIG. 8 is a top plan view of an inspection of a vehicle. The vehicle 210 has multiple sensors 80-89 that are located at important components of the vehicle 210 in relation to an assignment.

FIG. 9 is a flow chart for a method 915 for performing an electronic driver vehicle inspection report for an asset. At block 916, an assignment is received at an AMCD that is associated with an operator selected by the assigning authority to complete the assignment. At block 917, the assignment is initialized on the AMCD. At block 918, changes from an initial position at the asset are captured and stored. At block 919, the inspection of the asset is performed using the AMCD. At block 920, the inspection is completed.

FIG. 10 is a flow chart for a method 500 for remote profile management for utilizing data and computational information from on-vehicle and off-vehicle sources. At block 501, the contents of each of a plurality of databases are accessed by an assigning authority engine. At block 502, the contents are combined to produce a plurality of dynamic, temporal combinations of data elements and a plurality of instruction sets for a vehicle. At block 503, the plurality of dynamic, temporal combinations is executed. At block 504, data from a plurality of cloud sources comprising third party data and vehicle, timing, event, and/or positioning (“VTEP”) data is accessed to inform the plurality of instruction sets delivered by the assigning authority engine to the RPM. At block 505, one or more elements of the VTEP data is used as a basis to synchronize timing between the data, or computational outputs of two or more sources of electronic information. At block 506, a single coherent information picture is formed from fusing data and computational information from the on-vehicle and the off-vehicle sources.

A system 10 for securely connecting a wireless device to a single access point in a vehicle for a predetermined work assignment is shown in FIGS. 11 and 11A. The system 10 preferably comprises a remote server (cloud) 11, a vehicle gateway device 130, a smart device 110 and a passive device 61. The vehicle gateway device 130 is preferably a connected vehicle device (“CVD”).

The server/cloud 11 accesses dataset 12 and obtains driver information. Vehicle information, mobile device information (MAC address), passive device information (beacon ID) and other information to compile a SCP packet 14. At block 15, the server 11 provides SCP definitions to the vehicle gateway device 130 and the mobile device 110. At block 16 the server/cloud 11 authorizes the SCP. At block 17, the server/cloud 11 communicates with the vehicle gateway device 130.

The vehicle gateway device 130 uses datasets 22, with the beacon ID 23, a scan of wireless devices 24 along with the SCP definitions 26 received from the server/cloud 11 to compile a CVD compiled SCP packet 25. The CVD compiled SCP packet is sent to the cloud/server 11 at block 16 and authorization/validation of the CVD compiled SCP packet is received at block 27. At block 28 the SCP is authorized for broadcasting at the vehicle gateway device 130 a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. At block 29, the vehicle gateway device 130 communicates the broadcast with the server/cloud 11. At block 31, the vehicle gateway device 130 communicates with other devices, namely the smart device 110 over preferably a WiFi hotspot 32 and the passive device 61 by pairing using a BLUETOOTH communication protocol at block 33.

At block 49, the smart device (mobile device) 110 compiles a complied mobile device SCP packet from the SCP definitions 42, the data sets 48, the beacon ID 43, the Tablet ID 45, a driver ID 46, a vehicle ID 47 and scan of wireless devices 44. The mobile device 110 generates the hashed SSID and a passphrase from the complied mobile device SCP packet. At block 51, the mobile device 110 connects to the WiFi hotspot 32 of the vehicle device gateway 130.

The passive device 61 broadcast a unique ID at block 62 which is received by the mobile device 110 and the vehicle gateway device 130. At block 63, if a BLUETOOTH device, it broadcasts a BLUETOOTH advertisement at block 64.

The SCP is defined by an assigning authority in the server/cloud 11. The server/cloud 11 sends the SCP definition and any other required data in datasets to the CVD 130 and the mobile device 110. The CVD 130 adds the contextual data from local datasets to the sever-sent data to compile its SCP based definition. The local datasets include data wirelessly scanned from passive devices, preferably transmitting a BLUETOOTH beacon. Other local datasets include information from the vehicle. The CVD 130 sends its compiled SCP packet to the server 11 for authorization. The server 11 verifies the CVD compiled SCP packet, and if valid, the server 11 transmits a validation/approval signal to the CVD 130. The CVD then generates an access point SSID/passphrase with SCP. Likewise, the mobile device 110 utilizes contextual data from local datasets to compile its SCP based on the definitions. The mobile device 110 connects to the access point of the CVD 130 using the SCP. The CVD 130 and the mobile device 110 also connect to the passive device 61 since it is part of the SCP definition.

As used by the assigning authority engine 1105, a predetermined work assignment is a temporal event with a fixed start and completion based on assignable boundary conditions. The assignable boundary condition is at least one of a predetermined time period, a geographical destination, and a set route. Alternatively, the assignable boundary condition is any feature with a beginning and a termination. The assigning authority is performed by a person or persons, who have the appropriate authority and mechanisms to assign specific tasks and assets to a specific d vehicle operator or custodian, and to assign workflow assignments to same. The predetermined work assignment is assigned to a known person or entity that has its own primary networked device accessible through a password protected user interface, a specific name and password that auto-populates or otherwise automatically satisfies a plurality of credentials requirements, wherein the plurality of credential requirements are automatically available or revoked based on the assignable boundary condition identified in a pairing event.

The CVD 130 preferably broadcasts a WiFi wireless network with a hidden and hashed SSID unique to the host vehicle and protected by a unique, dynamically generated and hashed passphrase. The vehicle ID is entered into an application on the tablet that is then converted to the same hashed SSID and passphrase, which allows the tablet to attempt to connect to the corresponding CVD WiFi network and begin communication.

A method 900 for a secure connection to a wireless network of a vehicle is shown in FIG. 12 . At block 901, a server generates definitions for a SCP packet for assigning authority for a vehicle. At block 902 the server transmits the definitions for the SCP packet to a CVD and a mobile device. At block 903, the CVD compiles the SCP packet to generate a CVD compiled SCP. At block 904, the CVD transmits the CVD compiled SCP to the server for authorization. At block 905, the server transmits authorization for the CVD compiled SCP from to the CVD for creation of a validated SCP. At block 906, the mobile device generates a dataset to compile a mobile device compiled SCP. At block 907, the CVD broadcasts at a wireless network with a hidden and hashed SSID unique to the vehicle. The hidden and hashed SSID is generated from the validated SCP packet. At block 908, the mobile device generates the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. At block 909, the mobile device searches for a vehicle having the CVD broadcasting the wireless network in a hidden mode. At block 910, the mobile device securely connects with the CVD.

One embodiment utilizes a system for vehicle to mobile device secure wireless communications. The system comprises a vehicle 210, a CVD 130, a mobile device 110 and a passive communication device 61. The vehicle 210 comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine. The CVD 130 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The mobile device 110 comprises a graphical user interface, a mobile application, a processor, a WiFi radio, and a cellular network interface. The passive communication device 61 operates on a BLUETOOTH communication protocol. The server 11 is configured to generate a plurality of definitions for a SCP packet for assigning authority for the vehicle. The server 11 is configured to transmit the plurality of definitions for the SCP packet from the server to the CVD 130 and the mobile device 110. The CVD 130 is configured to compile the SCP packet to generate a CVD compiled SCP. The CVD 130 is configured to transmit the CVD compiled SCP to the server 11 for authorization. The server 11 is configured to transmit authorization for the CVD compiled SCP to the CVD 130 for creation of a validated SCP. The mobile device 110 is configured to generating a dataset to compile a mobile device compiled SCP. The CVD 130 is configured to broadcast a wireless network with a hidden and hashed SSID unique to the vehicle, the hidden and hashed SSID generated from the validated SCP packet. The mobile device 110 is configured to generate the hashed SSID and a passphrase from the dataset, which allows the mobile device connect to the wireless network. The mobile device 110 is configured to search for a vehicle having the CVD broadcasting the wireless network in a hidden mode. The mobile device 110 is configured to connect to the CVD 130 over the wireless network.

The dataset preferably comprises at least one of a plurality of definitions for the SCP packet, a tablet ID, a driver ID, a vehicle ID, a beacon ID, identified or defined entity/participant to the transaction, descriptions, actions, or states of thing, characteristics of identifiable devices, when present in a certain proximity and/or context.

Optionally, the mobile device 110 connects to a passive device, the passive device operating on a BLUETOOTH communication protocol. The passive device 61 is preferably a BLUETOOTH enabled device advertising a unique ID as a beacon or a complex system (speaker, computer, etc.) that emits BLUETOOTH enabled device advertising a unique ID as a beacon.

The mobile device 110 preferably receives input from a driver of the vehicle, and/or the server 11 contains the assigning authority that generates the SCP definitions.

The passive device 61 is preferably an internal device in the vehicle or an external device posted on a gate to a facility and generating a beacon. The beacon from the passive device is preferably a mechanism to ensure that the connection between the mobile device 110 and the CVD 130 occurs at a specific physical location dictated by the assigning authority through the server 11. Preferably, the automatic connection between the mobile device 110 and the CVD occurs because the assigning authority, through the server, has dictated that it occur.

As shown in FIG. 13 , a staging yard for trucks 210 a-201 d, each of a multitude of trucks 210 a-210 d broadcast a wireless signal for a truck specific network, with one truck 210 c broadcasting a wireless signal 225. However, the SSID is not published so unless a driver is already in possession of the SSID, the driver will not be able to pair the tablet computer 110 with the CVD 130 of the truck 210 to which the driver is assigned. So even though the wireless signals are being “broadcast”, they will not appear on a driver's tablet computer 110 (or other mobile device) unless the tablet computer 110 has already been paired with the CVD 130 of the vehicle 210. A driver 205 in possession of a tablet computer 110 pairs, using a signal 230, the tablet computer 110 with the wireless network 225 of the CVD of the truck 210 c, and thus the driver locates the specific truck 210 c he is assigned to in a parking lot full of identical looking trucks 210 a-d.

For example, on an IPHONE® device from Apple, Inc., the “UDID,” or Unique Device Identifier is a combination of forty numbers and letters, and is set by Apple and stays with the device forever.

For example, on an ANDROID based system, one that uses Google Inc.'s ANDROID operating system, the ID is set by Google and created when an end-user first boots up the device. The ID remains the same unless the user does a “factory reset” of the phone, which deletes the phone's data and settings.

The mobile communication device 110, or mobile device, is preferably selected from mobile phones, smartphones, tablet computers, PDAs and the like. Examples of smartphones and the device vendors include the IPHONE® smartphone from Apple, Inc., the DROID® smartphone from Motorola Mobility Inc., GALAXY S® smartphones from Samsung Electronics Co., Ltd., and many more. Examples of tablet computing devices include the IPAD® tablet computer from Apple Inc., and the XOOM™ tablet computer from Motorola Mobility Inc.

The mobile communication device 110 then a communication network utilized preferably originates from a mobile communication service provider (aka phone carrier) of the customer such as VERIZON, AT&T, SPRINT, T-MOBILE, and the like mobile communication service providers, provide the communication network for communication to the mobile communication device of the end user.

Wireless standards utilized include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

BLUETOOTH™ technology operates in the unlicensed 2.4 GHz band of the radio-frequency spectrum, and in a preferred embodiment the secondary device 30 and/or primary device 25 is capable of receiving and transmitting signals using BLUETOOTH™ technology. LTE Frequency Bands include 698-798 MHz (Band 12, 13, 14, 17); 791-960 MHz (Band 5, 6, 8, 18, 19, 20); 1710-2170 MHz (Band 1, 2, 3, 4, 9, 10, 23, 25, 33, 34, 35, 36, 37, 39); 1427-1660.5MH (Band 11, 21, 24); 2300-2700 MHz (Band 7, 38, 40, 41); 3400-3800 MHz (Band 22, 42, 43), and in a preferred embodiment the secondary device 30 and/or the primary device 25 is capable of receiving and transmitting signals using one or more of the LTE frequency bands. WiFi preferably operates using 802.11a, 802.11b, 802.11g, 802.11n communication formats as set for the by the IEEE, and in in a preferred embodiment the secondary device 30 and/or the primary device 25 is capable of receiving and transmitting signals using one or more of the 802.11 communication formats. Near-field communications (NFC) may also be utilized.

As shown in FIG. 14 , a typical mobile communication device 110 preferably includes an accelerometer 301, I/O (input/output) 302, a microphone 303, a speaker 304, a GPS chipset 305, a Bluetooth component 306, a Wi-Fi component 307, a 3G/4G component 308, RAM memory 309, a main processor 310, an OS (operating system) 311, applications/software 312, a Flash memory 313, SIM card 314, LCD display 315, a camera 316, a power management circuit 317, a battery 318 or power source, a magnetometer 319, and a gyroscope 320.

Each of the interface descriptions preferably discloses use of at least one communication protocol to establish handshaking or bi-directional communications. These protocols preferably include but are not limited to XML, HTTP, TCP/IP, Serial, UDP, FTP, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS and Flash. Databases that may be used with the system preferably include but are not limited to MSSQL, Access, MySQL, Progress, Oracle, DB2, Open Source DBs and others. Operating system used with the system preferably include Microsoft 2010, XP, Vista, 200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I series, AS 400 and Apple OS.

The underlying protocol at the cloud server 11, is preferably Internet Protocol Suite (Transfer Control Protocol/Internet Protocol (“TCP/IP”)), and the transmission protocol to receive a file is preferably a file transfer protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Secure Hypertext Transfer Protocol (“HTTPS”) or other similar protocols. The transmission protocol ranges from SIP to MGCP to FTP and beyond. The protocol at the authentication server 40 is most preferably HTTPS.

Wireless standards include 802.11a, 802.11b, 802.11g, AX.25, 3G, CDPD, CDMA, GSM, GPRS, radio, microwave, laser, Bluetooth, 802.15, 802.16, and IrDA.

Components of a cloud computing server 40 of the system, as shown in FIG. 15 , preferably includes a CPU component 401, a graphics component 402, PCI/PCI Express 403, memory 404, non-removable storage 407, removable storage 408, Network Interface 409, including one or more connections to a fixed network, and SQL database(s) 45 a-45 d, which includes the venue's CRM. Included in the memory 404, is an operating system 405, a SQL server 406 or other database engine, and computer programs/software 410. The server 40 also preferably includes at least one computer program configured to receive data uploads and store the data uploads in the SQL database. Alternatively, the SQL server can be installed in a separate server from the server 40.

A flow chart for an alternative method 600 for a secure connection to a wireless network of a vehicle is shown in FIG. 16 . At block 601, the CVD broadcasts an encrypted, blind SSID based on specific vehicle data. At block 602, leveraging the known vehicle data and the encryption algorithm a mobile device searches for a vehicle having a CVD broadcasting the wireless network. At block 603, the mobile device is connected with the CVD.

As shown in FIG. 17 , a staging yard for trucks 210 a-210 k, each of a multitude of trucks 210 a-210 k broadcast a wireless signal 224 a-k for a truck specific network, with one truck 210 f broadcasting a wireless signal 225. However, all of the wireless signal 224 a-224 k and 225 do not publish their respective SSID so that a mobile device 110 must already be paired with the CVD 130 of the truck 210 in order to connect to the truck based wireless network 224 a-224 k or 225 of each of the CVDs 130 of each of the trucks 210 a-210 k. A driver 205 in possession of a tablet computer 110 pairs with the specific truck wireless network 225 of the CVD 130 of the truck 210 f, and thus the driver locates the specific truck 210 f he is assigned to in a parking lot full of identical looking trucks 210 a-210 k.

One embodiment is a system for utilizing a remote profile manager for vehicle dynamic compliance with multiple vehicle statutes and regulations. The system comprises a truck 210, a CVD 130, a tablet computer 110, a server 140 and a plurality of databases. The vehicle comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine. The CVD 130 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The tablet computer 110 comprises a graphical user interface, a processor, a WiFi radio, a BLUETOOTH radio, and a cellular network interface. A location of the truck 210 is determined using a GPS component of the truck 210. The location of the truck 210 is transmitted to the server 140 by the CVD. The server 140 retrieves real-time compliance rules for the location of the truck from the plurality of databases, which are preferably State vehicle databases, municipal vehicle databases, county vehicle databases, and Federal vehicle databases. The server 140 transmits the real-time compliance rules to CVD 130 for display on the tablet computer 110 so that a driver of the truck 210 can stay in real-time compliance with State and Federal motor vehicle and driving rules. The rules pertain to speed limits, transport of toxic waste, the transport of refrigerated cargo, the rest durations for drivers, the necessary insurance coverage, the type of taxes and fees to be paid, and the like. The display on the tablet computer is preferably in the form of a visual alert, an audio alert or a haptic alert. Other displays include forms such as attestation forms, and data such as timers, current speed limits, and the like. The trigger for each jurisdiction is preferably from the GPS of the truck 210, the speed of the truck 210, cellular or WiFi triangulation from a network, and the like.

The CVD 130 obtains the vehicle identification number (VIN) from the on-board computer and transmits the VIN with the location to the server 140 for verification of the truck 210.

Another embodiment is a system for utilizing a remote profile manager for utilizing multiple vehicle odometer values. The system comprises a vehicle 210, a CVD 130, a tablet computer 110, a server 140 and a plurality of databases. The vehicle comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, a motorized engine, an odometer component from an engine source, an odometer component from a dashboard source, an odometer component from a chassis source, and an odometer component from a transmission source. Thus, the truck 210 has a multiple of odometers that can be used to determine a mileage of the truck 210. The connected vehicle device (CVD) 130 comprises a processor, a WiFi radio, a BLUETOOTH radio, a memory, and a connector for mating with the connector plug of the vehicle. The tablet computer 110 comprises a graphical user interface, a processor, a WiFi radio, a BLUETOOTH radio, and a cellular network interface. Each of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source generates an odometer value. The CVD 130 generates a delta value for odometer value relative to a control odometer value. The CVD 130 monitors the odometer value from each of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source. The CVD 130 generates a new odometer value for one of the odometer component from an engine source, the odometer component from a dashboard source, the odometer component from a chassis source, and the odometer component from a transmission source, and the CVD modifies the odometer value by the delta value to generate the new odometer value.

An operating system controls the execution of other computer programs, running of the PSO platform, and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. The operating system may be, for example Windows (available from Microsoft, Corp. of Redmond, Wash.), LINUX or other UNIX variants (available from Red Hat of Raleigh, N.C. and various other vendors), Android and variants thereof (available from Google, Inc. of Mountain View, Calif.), Apple OS X, iOs and variants thereof (available from Apple, Inc. of Cupertino, Calif.), or the like.

The system and method described in connection with the embodiments disclosed herein is preferably embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module preferably resides in flash memory, ROM memory, EPROM memory, EEPROM memory, RAM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is preferably coupled to the processor, so that the processor reads information from, and writes information to, the storage medium. In the alternative, the storage medium is integral to the processor. In additional embodiments, the processor and the storage medium reside in an Application Specific Integrated Circuit (ASIC). In additional embodiments, the processor and the storage medium reside as discrete components in a computing device. In additional embodiments, the events and/or actions of a method reside as one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer-readable medium, which are incorporated into a computer software program.

In additional embodiments, the functions described are implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions are stored or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium is any available media that is accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures, and that can be accessed by a computer. Also, any connection is termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. “Disk” and “disc”, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and BLU-RAY disc where disks usually reproduce data magnetically, while discs usually reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable medium.

A computer program code for carrying out operations of the Present Invention is preferably written in an object oriented, scripted or unscripted programming language such as C++, C#, SQL, Java, Python, Javascript, Typescript, PHP, Ruby, or the like.

Each of the interface descriptions preferably discloses use of at least one communication protocol to establish handshaking or bi-directional communications. These protocols preferably include but are not limited to XML, HTTP, TCP/IP, Serial, UDP, FTP, Web Services, WAP, SMTP, SMPP, DTS, Stored Procedures, Import/Export, Global Positioning Triangulation, IM, SMS, MMS, GPRS and Flash. The databases used with the system preferably include but are not limited to MSSQL, Access, MySQL, Oracle, DB2, Open Source DBs and others. Operating system used with the system preferably include Microsoft 2010, XP, Vista, 200o Server, 2003 Server, 2008 Server, Windows Mobile, Linux, Android, Unix, I series, AS 400 and Apple OS.

The underlying protocol at a server, is preferably Internet Protocol Suite (Transfer Control Protocol/Internet Protocol (“TCP/IP”)), and the transmission protocol to receive a file is preferably a file transfer protocol (“FTP”), Hypertext Transfer Protocol (“HTTP”), Secure Hypertext Transfer Protocol (“HTTPS”), or other similar protocols. The protocol at the server is preferably HTTPS.

Components of a server includes a CPU component, a graphics component, memory, non-removable storage, removable storage, Network Interface, including one or more connections to a fixed network, and SQL database(s). Included in the memory, is an operating system, a SQL server or other database engine, and computer programs/software.

-   Kennedy et al., U.S. patent No. 11197329 for a Method And System For     Generating Fueling Instructions For A Vehicle, is hereby     incorporated by reference in its entirety. -   Kennedy et al., U.S. patent No. 10652935 for Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent No. 11330644for Secure Wireless Networks     For Vehicle Assigning Authority, is hereby incorporated by reference     in its entirety. -   Kennedy et al., U.S. patent application Ser. No. 10917921, for     Secure Wireless Networks For Vehicles, is hereby incorporated by     reference in its entirety. -   Son et al., U.S. patent Ser. No. 10/475,258 for a Method And System     For Utilizing Vehicle Odometer Values And Dynamic Compliance, is     hereby incorporated by reference in its entirety. -   Son et al., U.S. patent Ser. No. 10/070,471 for a Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Son et al., U.S. patent Ser. No. 10/652,935 for a Secure Wireless     Networks For Vehicles, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent No. 11197330, for a Remote Profile     Manager For A Vehicle, is hereby incorporated by reference in its     entirety. -   Kennedy et al., U.S. patent Publication No. 20200413458, for a     Micro-Navigation For A Vehicle, is hereby incorporated by reference     in its entirety.

From the foregoing it is believed that those skilled in the pertinent art will recognize the meritorious advancement of this invention and will readily understand that while the present invention has been described in association with a preferred embodiment thereof, and other embodiments illustrated in the accompanying drawings, numerous changes modification and substitutions of equivalents may be made therein without departing from the spirit and scope of this invention which is intended to be unlimited by the foregoing except as may appear in the following appended claim. Therefore, the embodiments of the invention in which an exclusive property or privilege is claimed are defined in the following appended claims. 

We claim as our invention the following:
 1. A system for capturing the proper execution of a series of one or more tasks with pre-assigned constraints that are associated with at least one asset, the system comprising: at least one asset comprising a plurality of physical attributes and characteristics in a known configuration; and a mobile device comprising a wireless transceiver, a processor for onboard processing, a memory, at least one user interface and a plurality of positional detecting components; wherein the mobile device is configured to capture the execution of a series of one or more tasks with pre-assigned constraints that are associated with the at least one asset.
 2. The system according to claim 1 wherein the wireless transceiver has radio frequency capabilities for at least one of WiFi, Bluetooth, 3G/LTE/5G, or GPS, and the at least one user interface comprises a touch input or a voice to text input.
 3. The system according to claim 1 wherein the asset or mobile device further comprises a plurality of sensors.
 4. The system according to claim 3 wherein the plurality of sensors comprises at least one of movement, thermal, pressure, proximity, moisture or vibration sensing capabilities.
 5. The system according to claim 1 wherein the plurality of positional detecting components comprises at least of one of a gyroscope, an accelerometer, a magnetometer or another compass heading source capable of computing positioning in 3 axis, changes to position in 3 axis, distance and path taken as changes are being computed.
 6. The system according to claim 1 wherein the mobile device connects to a secure wireless network of the asset.
 7. The system according to claim 1 wherein the mobile device validates in real time that the assets being evaluated are geographically co-located with the authorized mobile computing device (AMCD) within assigning authority configured proximity definitions.
 8. The system according to claim 1 wherein the asset is a vehicle and the vehicle comprises an on-board computer with a memory having a vehicle identification number (VIN), a connector plug, and a motorized engine.
 9. The system according to claim 1 wherein an operator of the at least one asset must satisfy a configurable plurality of conditions before beginning an assigned task, wherein the plurality of conditions comprises vehicle or asset(s) position or state, driver status, an AMCD state, and assignment initialization status.
 10. The system according to claim 7 wherein the mobile device validates in real time that the at least one asset being evaluated is geographically co-located with the AMCD within an assigning authority configured proximity definition.
 11. The system according to claim 7 wherein the mobile device contemporaneously validates during the period of assignment completion specific information such as the vehicle identification number, serial number, or other discrete high-confidence identifying information that confirms that the assets being evaluated are the appropriate discrete assets identified in the assignment.
 12. A method of using a mobile device to capture the execution of a series of one or more tasks with pre-assigned constraints that are associated with one or more specific assets, where those assets have certain known physical attributes and characteristics in a known configuration.
 13. The method according to claim 12 wherein the mobile device is a tablet computer.
 14. The method according to claim 12 wherein the mobile device connects to a wireless network of a vehicle.
 15. The method according to claim 12 wherein the Operator must satisfy a configurable set of conditions before beginning the assigned tasks, conditions including vehicle or asset(s) position or state, Driver status, AMCD state, and Assignment Initialization status.
 16. The method according to claim 12 wherein the mobile device validates in real time that the assets being evaluated are geographically co-located with the AMCD within assigning authority configured proximity definitions.
 17. The method according to claim 12 wherein the mobile device contemporaneously validates during the period of assignment completion specific information such as the vehicle identification number, serial number, or other discrete high-confidence identifying information that confirms that the assets being evaluated are the appropriate discrete assets identified in the assignment.
 18. A system for an electronic driver vehicle inspection report for an asset, the system comprising: a mobile device comprising a processor, a graphical user interface, a memory, one or more sensors, a wireless transceiver and a mobile application; and an asset comprising a plurality of set inspection points, each of the plurality of set inspection points are at a known position on the asset and physically uniquely positioned from any other of the plurality of set inspection points; wherein the mobile application is configured to utilize at least one of the sensors to verify an inspection of an inspection point of the plurality of set inspection points when the mobile device is within a pre-determined distance from the inspection point.
 19. The system according to claim 18 wherein the asset further comprises a plurality of sensors.
 20. The system according to claim 19 wherein the plurality of sensors comprises at least two of a movement sensor, a proximity sensor, a thermal sensor, a pressure sensor, a moisture sensor or a vibration sensor.
 21. The system according to claim 18 wherein the mobile device further comprises a plurality of positional detecting components comprising at least one of a gyroscope, an accelerometer, a magnetometer or another compass heading source.
 22. The system according to claim 18 wherein the mobile device validates in real time that the at least one asset being evaluated is geographically co-located with the authorized mobile computing device (AMCD) within an assigning authority configured proximity definitions and wherein the mobile device connects to a secure wireless network of a vehicle.
 23. The system according to claim 18 wherein the wireless transceiver is a WiFi transceiver, a Bluetooth transceiver, a 3G/LTE/5G transceiver, a GPS receiver, or their variations and/or evolutions.
 24. The system according to claim 18 wherein the asset is a trailed vehicle.
 25. The system according to claim 18 wherein the mobile device connects to a secure wireless network.
 26. A method for performing an electronic driver vehicle inspection report for an asset, the method comprising: receiving an assignment at an authorized mobile computing device (AMCD) that is associated with an operator selected by the assigning authority to complete the assignment; initializing the assignment on the AMCD; capturing and storing changes from an initial position at the asset; performing the inspection of the asset using the AMCD; and completing the inspection.
 27. The method according to claim 26 wherein the capturing and storing changes from an initial position at the asset comprises an accelerometer state and at least one of a magnetometer and/or other compass heading source data current position information, or decibel and bearing information from a known radio frequency source.
 28. The method according to claim 26 further comprising creating a plurality of discrete sequence positions, each of which describe a series of positions using data generated by the accelerometer, magnetometer or decibel and bearing information, at any discrete point in time, with a naming convention that allows these positions to be reassembled at any time subsequent to their capture, in an order that replicates the geospatial position of the AMCD at the time of the capture of each sequence position.
 29. The method according to claim 26 wherein the asset is a physical asset with certain physical attributes known to the assignment, that are configured in a manner that is known to the assignment, and whose configuration and known physical attributes associated with the temporal configuration existing during the time the group of tasks are being executed, can be used to calculate constraints to the execution of the group of tasks.
 30. The method according to claim 29 further comprising contemporaneously validating a source during the period of assignment completion specific information such as the vehicle identification number, serial number, or other discrete high-confidence identifying information that confirms that the assets being evaluated are the appropriate discrete assets identified in the assignment, and no others. 